home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950726-19950929
/
000136_news@columbia.edu_Thu Aug 10 01:07:57 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA08875
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Fri, 11 Aug 1995 01:11:39 -0400
Received: by apakabar.cc.columbia.edu id AA16618
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Fri, 11 Aug 1995 01:11:37 -0400
Path: news.columbia.edu!news.cs.columbia.edu!pipeline!newsjunkie.ans.net!gatech!newsfeed.internetmci.com!news.sprintlink.net!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MS KERMIT, telnet, and WFW
Message-Id: <1995Aug10.070757.58553@cc.usu.edu>
Date: 10 Aug 95 07:07:57 MDT
References: <40cf50$9p6@usenet.INS.CWRU.Edu>
Organization: Utah State University
Lines: 31
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <40cf50$9p6@usenet.INS.CWRU.Edu>, cn125@cleveland.Freenet.Edu (Jerry L. Brod) writes:
> I'm trying to use MS-DOS Kermit to make telnet connections
> from Microsoft Windows for Workgroups 3.11. I have examined
> the MSKWFW.DOC file and found that our situation seems to be
> covered by text #3, situation 3: WFW uses NDIS version 3 handler
> and its own TCP/IP stack. The text states:
>
> An alternative for those owning the Microsoft TCP/IP
> protocol stack is to run Kermit over that stack. The
> Kermit command to do this is SET PORT 3COM(BAPI), and
> that talks to WFW protected-mode agent VBAPI.386.
> Host selection occurs while talking to the BAPI handler
> itself. Shims are not needed in this case.
>
> This seems like an ideal solution, but I'm unable to find the
> VBAPI.386 handler in Microsoft's WFWT32.EXE archive. It does
> exist in the older WFWTCP.EXE archive, but that version does
> not support the 32-bit protected mode tcp stack that we want
> to run. The notes with the WFWT32 archive indicate that it
> is a complete refresh of WFWTCP. Did Microsoft drop support
> of BAPI?
----------
The answer seems to be yes to your last (BAPI) question.
Dan Lanciani at Harvard has been working on a shim for this situation,
the archive file is named ndis3pkt.zip, so please contact him at
ddl@harvard.edu. An older version is in directory drivers on netlab2.usu.edu,
but please be aware that the rules on MS' TCPIP32 have been very fluid
and this older version is probably inappropriate.
A cheap solution is to add a second Ethernet board, as silly
as that first appears.
Joe D.